Organizations

This guide explains how a platform customer can use the v0 Platform API with Vercel Organizations to offer v0-style chat experiences to their own customers.

The model

The integration uses three layers:

Recommended mapping: one child team per customer account or workspace.

Prerequisites

Before using this flow:

1. The parent team must be on Enterprise Flex Commit.
2. The parent team owner must have the v0 Builder role.
   • Can be granted at vercel.com/team-slug/~/settings/members
3. Create a Vercel API token at vercel.com/account/settings/tokens with Full Account scope.
   • This should be done by the parent team owner.
4. The parent team must be allowlisted for Organizations and v0 Platform API access.

Setup flow

1. Create an organization

Create a Vercel Organization attached to the Enterprise Flex Commit parent team.

const organization = await fetch("https://api.vercel.com/v1/organizations", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.VERCEL_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    teamId: "team_parent",
    slug: "acme-platform",
  }),
}).then((res) => res.json())

2. Create a parent v0 API key

Create a parent-team API key at v0.app/settings/keys.

Use this key to:

• Create API keys for child teams
• Set organization and child-team spend limits

3. Create customer teams

For each customer, create a new Vercel team under the organization.

const customerTeam = await fetch("https://api.vercel.com/v1/teams", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.VERCEL_TOKEN}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    organizationId: organization.organizationId,
    slug: "acme-customer-123",
    name: "Acme Customer 123",
  }),
}).then((res) => res.json())

Store the returned teamId; it becomes the customer's child team for v0 isolation, usage, and limits.

4. Create a child-team v0 API key

Use the parent v0 API key to create an API key scoped to the child team.

const childApiKey = await fetch(
  `https://api.v0.app/v2/organizations/${organization.organizationId}/teams/${customerTeam.id}/api-keys`,
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.PARENT_V0_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      name: "Production Key",
    }),
  },
).then((res) => res.json())

The response returns the child team's API key once. Store it as a customer-scoped secret.

5. Use the child-team key for chats

Use the child team's API key for that customer's chat operations.

const chat = await fetch("https://api.v0.app/v2/chats", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${childApiKey.key}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    prompt: "Create a landing page",
    metadata: {
      internalUserId: "user_123",
    },
  }),
}).then((res) => res.json())

Chat and message responses include usage data. Use the returned usage payload for real-time customer usage tracking.

Billing and spend limits

• Child-team invoices roll up to the parent team.
• Organization-level spend limits apply by default to child teams.
• Team-level spend limits override the organization-level limit.
• Limits reset monthly.
• There are no separate usage endpoints. Usage is returned directly in chat and message responses.

Use organization-level limits for broad guardrails and team-level limits for customer-specific caps.

Access and isolation

Metadata can be used for attribution and analytics, but it is not an access-control boundary. The team remains the isolation boundary.

What to store

Store these values securely:

Important notes

• Do not use the Vercel invite API for this flow. Usage should be attributed to teams, not individual invited users.
• Keep the parent team separate from internal-use teams when possible.
• Treat API keys as unrecoverable secrets.